-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Response Ops] Using data view service to fetch data views #131330
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes LGTM! Tested locally and it works 👍
@elasticmachine merge upstream |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spring cleaning LGTM :)
💚 Build SucceededMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @ymao1 |
Co-authored-by: Kibana Machine <[email protected]>
Resolves #129914
Summary
Using data view service to fetch index patterns instead of using the saved objects client directly. Previously, when using the saved objects client, we retrieved 1000 data views at a time and paginated if the total number of matching data views exceeded 1000. The data views service does not provide the ability to specify page number so functionality for this changes a bit as
loadIndexPatterns
will now only return up to 1000 matching data views. Discussed with the team and we felt that this should be sufficient, especially since the data views are filtered based on user input.To Verify
Verify that selecting index pattern for Index Threshold and ES Query rule type still work as expected. Also verify that selecting index pattern for ES Index connector type works as expected.
Checklist